Downgrade iOS?

How do I downgrade from iOS 10 to a reasonably recent version of 9?


The update to iOS 10 made some of my alarms silent--selectively. Only the alarms that I rely on to wake me in the morning were silenced. It did not affect the evening alarm that I used to test if that had been the problem (e.g., it is giving false negatives). Since the alarm functionality is fundamental to the phone, this is unacceptable.


So, until Apple manages to release a version of iOS 10 that doesn't kill fundamental features of the phone, I need to get back to some iteration of iOS 9. ASAP. I can't afford to risk my alarm not waking me up for a third day in a row to find out if they have addressed the issue.

Posted on Sep 27, 2016 1:12 PM

Reply
8 replies

Sep 27, 2016 1:19 PM in response to Alliumcepa

The alarm issue has not been reported by anyone, so I doubt its something inherently wrong with the update and more something specific with your device or iOS installation, in which case Apple would be unable to do anything about it.


As there is no way to go back to a previous iOS version I would do as Tim above suggests, and perform some troubleshooting on your device:


  1. A Reset may cure some bugs. Hold down the Home and sleep/power buttons until the apple logo shows up.

    If still not resolved:

  2. Reste al Settings. Go to Settings->General->Reset->Reset All Settings

    If its still not resolved:

  3. Restore the device as new.
    Use iTunes on your Mac or PC to restore your iPhone, iPad, or iPod to factory settings - Apple Support

Sep 27, 2016 1:21 PM in response to KiltedTim

I have tried troubleshooting it. Why else would I know that only some of my alarms are silenced?


The only unifying theme is that those that use the "Classic" alarm tones (specifically, "Alarm" in the Classic menu) are silenced, while those that use the more recent tones are not. Unfortunately, the more recent tones are not jarring enough to wake me up reliably.

Sep 27, 2016 1:34 PM in response to Phil0124

I appreciate that you were more specific regarding troubleshooting steps. I had gone through (1) already, but not (2) or (3)--yet. However, the only reliable check for effective resolution can be performed only once per 24-hour cycle, with an all-or-nothing feedback (and significant consequences for failure). Obviously, this presents problems that are overlooked in the response.


And, it seems a little quick to presume that because the issue has not been reported by others--in an iOS that is barely over 10 days old, and likely less than 100% reporting--that there is nothing "inherently wrong with the update" and that "Apple would be unable to do anything about it" as the entity that produced the phone, the operating system, and verified or directly produced all of the apps. The level of control Apple has over the device would belie the notion that Apple could disclaim all responsibility.


That being said, I also recognize that Apple has good attorneys, and has effectively disclaimed all liability (even if they cannot disclaim responsibility outside the legal sphere). As such, I know that my only recourse would be ending my 9 year stint as an iPhone user.

Sep 27, 2016 1:35 PM in response to Alliumcepa

Just tested this, and the "Alarm" sound from the classic menu sounded fine at the set time.


I would suggest a restore, as it is conceivable the sound files for those alarms may be corrupted, and a complete restore would fix that by reloading the files onto the phone.


Use iTunes on your Mac or PC to restore your iPhone, iPad, or iPod to factory settings - Apple Support

Sep 27, 2016 5:17 PM in response to Phil0124

Update:


The "Alarm" sound file is fine.


I figured out a method to figure out whether it will be an audible alarm, or if it will merely vibrate, and it appears that the sound file is unaffected. The issue was that some of the existing alarm files (or their paths to the database of sounds) were corrupted by the update. Adjusting the time of the alarm or the sound file sought to be used by the alarm did not resolve the issue, but deleting the alarm and creating a replacement alarm restored sound.


Still perplexing, but resolved: the update to iOS 10 may require deleting prior alarms and replacing them with newly-entered alarms to restore functionality of this feature.


Purely speculation, but since some (but not all) of these alarm files have been maintained and copied from a prior iPhone, it may be that the update to iOS 10 ported over more recent code to a new format, but did not adjust older ones (where the files were not materially adjusted due to more minor changes to the base code). This would, at least, explain why some retained functionality while others didn't.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Downgrade iOS?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.